Method, msg in 5g server, and non-msg in 5g gateway for providing messaging service in 5g system

ABSTRACT

The present disclosure relates to a pre-5th generation (5G) or 5G communication system to be provided for supporting higher data rates beyond 4th generation (4G) communication system such as long term evolution (LTE). Embodiments herein provide a method, an MSGin5G server , and non-MSGin5G gateway for providing messaging service in 5th generation system. The provided method provides a TRF which can assist the MSGin5G server to determine a transport service(s), a GWSF which can assist the MSGin5G server to determine appropriate gateway for the determined transport service(s). Further, the provided method includes a TF to translate the MSGin5G message to a legacy 3GPP message format or a non-3GPP message format.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on and claims priority under 35 U.S.C. §119(a) of an Indian Provisional patent application number 202041037179filed on August 28, 2020, in the Indian Patent Office, and an IndianNon-Provisional patent application number 202041037179 filed on Aug. 13,2021, in the Indian Patent Office, the disclosure of each of which isincorporated by reference herein in its entirety.

BACKGROUND 1. Field

The present disclosure relates to a wireless network, and morespecifically related to a method, an MSGin5G server, and a non-MSGin5Ggateway for providing messaging service in 5G system.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4th generation (4G) communication systems, efforts havebeen made to develop an improved 5th generation (5G) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post LTE System’.

The 5G communication system is considered to be implemented in higherfrequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higherdata rates. To decrease propagation loss of the radio waves and increasethe transmission distance, the beamforming, massive multiple-inputmultiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are discussed in5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud RadioAccess Networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul, moving network, cooperativecommunication, Coordinated Multi-Points (CoMP), reception-endinterference cancellation and the like.

In the 5G system, Hybrid FSK and QAM Modulation (FQAM) and slidingwindow superposition coding (SWSC) as an advanced coding modulation(ACM), and filter bank multi carrier(FBMC), non-orthogonal multipleaccess(NOMA), and sparse code multiple access (SCMA) as an advancedaccess technology have been developed.

In general, 3rd generation partnership project (3GPP) is presentlydescribing message in 5th generation (MSGin5G) application service as amessaging service in a 5G system. Application architecture for theMSGin5G application service, as specified in 3GPP TS 23.554, isanticipated to support a variety of user equipment (UE) types, based onunderlying transport services (e.g., an MSGin5G transport service, anon-MSGin5G transport service) supported by the UE. The UE types includean MSGin5G UE, a Legacy 3GPP UE, and a Non-3GPP UE.

The MSGin5G UE supports MSGin5G client and is able to send an MSGin5Gmessage payload. While the legacy 3GPP UE does not support MSGin5G andinstead uses one of the 3GPP-defined message delivery mechanisms (e.g.,short message service (SMS), a non-IP data delivery (NIDD), broadcast,etc.). Furthermore, the non-3GPP UE does not support the MSGin5G clientbut does support one of the non-3GPP message delivery mechanisms (e.g.,a rich communication services (RCS) and a lightweightM2M (LwM2M), etc.).Thus, it is desired to provide a useful alternative for deliveringmessage/MSGin5G message payload in the 5G system.

The principal object of the embodiments herein is to determine whether atarget UE supports an MSGin5G transport service using a targetresolution function (TRF) of an MSGin5G server upon receiving an MSGin5Gmessage request from a source UE to deliver a message to the target UEin a wireless network. Further, the MSGin5G server sends the message tothe target UE in response to determining that the target UE supports theMSGin5G transport service. Furthermore, the MSGin5G server selects anon-MSGin5G gateway in the wireless network using a gateway selectionfunction (GWSF) of the MSGin5G server in response to determining thatthe target UE does not support the MSGin5G transport service.Furthermore, the MSGin5G server sends the message to the non-MSGin5Ggateway, where the non-MSGin5G gateway translates the MSGin5G messagerequest according to a non-MSGin5G transport service using a translationfunction (TF) of the non-MSGin5G gateway and the non-MSGin5G gatewaysends the message to the target UE after translation. As a result, evenif the target UE does not support an MSGin5G message payload/MSGin5Gclient, the source UE (i.e., MSGin5G UE) sends the message to the targetUE (e.g., MSGin5G UE, Legacy 3GPP UE, Non-3GPP UE, etc.) and the targetUE does not require any external hardware to communicate with the sourceUE.

Another object of the embodiment herein is to determine whether thetarget UE is registered in a MSGin5G UE registration repository of theMSGin5G server. Furthermore, the MSGin5G server detects that the targetUE supports the MSGin5G transport service in response to determiningthat the target UE is registered in the MSGin5G UE registrationrepository of the MSGin5G server. Furthermore, the MSGin5G serverdetects that the target UE supports the non-MSGin5G transport service inresponse to determining that the target UE is not registered in theMSGin5G UE registration repository of the MSGin5G server.

Another object of the embodiment herein is to detect that the target UEis one of a legacy 3GPP UE and a non-3GPP UE based on a UE registrationrepository of a home subscriber MSGin5G server (HSS) and/or a unifieddata management (UDM) in a wireless network.

SUMMARY

Accordingly, embodiments herein disclose a method for delivering a 5thgeneration messages (MSGin5G) in a wireless network. The method includesreceiving, by an MSGin5G server, an MSGin5G message request from asource UE to deliver a message to a target UE in the wireless network.Further, the method includes determining, by the MSGin5G server, whetherthe target UE supports an MSGin5G transport service using a TRF (basedon MSGin5G service identity of the target UE) of the MSGin5G server uponreceiving the MSGin5G message request from the source UE. Further, themethod includes sending the message to the target UE in response todetermining that the target UE supports the MSGin5G transport service.Further, the method includes selecting a non-MSGin5G gateway in thewireless network using a GWSF of the MSGin5G server in response todetermining that the target UE does not support the MSGin5G transportservice. Further, the method includes sending the message to thenon-MSGin5G gateway, where the non-MSGin5G gateway translates theMSGin5G message request according to a non-MSGin5G transport serviceusing a TF of the non-MSGin5G gateway and the non-MSGin5G gateway sendsthe message to the target UE after translation.

In an embodiment, the MSGin5G message request comprises an MSGin5Gservice identify (ID) of the source UE, an MSGin5G service ID of thetarget UE, and message ID information, a delivery status, an applicationID, a payload, and priority type information elements.

In an embodiment, the non-MSGin5G transport service comprises a legacy3GPP transport service and/or a non-3GPP transport service.

In an embodiment, the non-MSGin5G gateway comprises a legacy 3GPPmessage gateway and/or a non-3GPP message gateway.

In an embodiment, the legacy 3GPP message gateway is used to deliver themessage to the target UE using the 3GPP transport service and thenon-3GPP message gateway is used to deliver the message to the target UEusing the non-3GPP transport service.

In an embodiment, the source UE is an MSGin5G UE and the target UE isthe MSGin5G UE and a non-MSGin5G UE, and where the MSGin5G UE supportsthe MSGin5G transport service and the target UE supports the MSGin5Gtransport service and/or the non-MSGin5G transport service.

In an embodiment, the non-MSGin5G UE is a legacy 3GPP UE and/or anon-3GPP UE.

In an embodiment, where determining, by the MSGin5G server, whether thetarget UE supports the MSGin5G transport service using the TRF (based onMSGin5G service identity of the target UE) of the MSGin5G server uponreceiving the MSGin5G message request from the source UE includesdetermining, by the MSGin5G server, whether the target UE is registeredin a MSGin5G UE registration repository of the MSGin5G server. Further,the method includes detecting that the target UE supports the MSGin5Gtransport service in response to determining that the target UE isregistered in the MSGin5G UE registration repository of the MSGin5Gserver. Further, the method includes detecting that the target UEsupports the non-MSGin5G transport service in response to determiningthat the target UE is not registered in the MSGin5G UE registrationrepository of the MSGin5G server.

In an embodiment, where detecting that the target UE supports the legacy3GPP transport service includes detecting, by the MSGin5G server, thatthe target UE is registered in a UE registration repository of an HSSand/or a UDM in the wireless network.

In an embodiment, where detecting that the target UE supports thenon-3GPP transport service includes detecting, by the MSGin5G server,that the target UE is not registered in the MSGin5G UE registrationrepository and is not registered in a registration repository of the HSSand/or the UDM in the wireless network

In an embodiment, where selecting the non-MSGin5G gateway in thewireless network using the GWSF of the MSGin5G server includesselecting, by the MSGin5G server, one of the legacy 3GPP message gatewayand the non-3GPP message gateway based on the mapping table available atthe GWSF. Further, the method includes performing, by the MSGin5Gserver, an authentication of the source UE. Further, the method includessending, by the MSGin5G server, the message to one of the legacy 3GPPmessage gateway and the non-3GPP message gateway based on selection.

In an embodiment, where translating the MSGin5G message requestaccording to non-MSGin5G transport service using the TF includesdetecting, by the MSGin5G server, that the legacy 3GPP message gatewayis selected. Further, the method includes determining, by the legacy3GPP message gateway, a message delivery mechanism to send the messageto the target UE based on a capability of the target UE, a communicationstatus of the target UE, and a service configuration of the target UE,where the message delivery mechanism is one of an SMS and a NIDD.Further, the method includes performing, by the legacy 3GPP messagegateway, registration and de-registration with the MSGin5G server forthe non-MSGin5G UE. Further, the method includes performing, by thelegacy 3GPP message gateway, a segmentation of the message andreassembling of the message for the non-MSGin5G UE. Further, the methodincludes performing, by the legacy 3GPP message gateway, conversion ofan address of the target UE. Further, the method includes translating,by the legacy 3GPP message gateway, protocols, and non-message payloadinformation of the message based on the determined message deliverymechanism. Further, the method includes sending, by the legacy 3GPPmessage gateway, the message to the target UE.

In an embodiment, the legacy 3GPP message gateway receives deliveryreport from the target UE and translate the received delivery reportinto an MSGin5G message delivery report and sends an MSGin5G messagedelivery report to the MSGin5G server.

In an embodiment, where translating the MSGin5G message requestaccording to non-MSGin5G transport service using the TF includesdetecting, by the MSGin5G server, that the non-3GPP message gateway isselected. Further, the method includes determining, by the non-3GPPmessage gateway, a message delivery mechanism to send the message to thetarget UE based on a capability of the target UE, a communication statusof the target UE, and a service configuration of the target UE, wherethe message delivery mechanism is one of an RCS and an LwM2M. Further,the method includes translating, by non-3GPP message gateway, themessage into a non-3GPP message based on the determined message deliverymechanism. Further, the method includes sending, by the non-3GPP messagegateway, the message to the target UE.

In an embodiment, the non-3GPP message gateway receives a deliveryreport from the target UE and translates the received delivery reportinto an MSGin5G message delivery report and sends an MSGin5G messagedelivery report to the MSGin5G server.

Accordingly, embodiments herein disclose the MSGin5G server fordelivering the MSGin5G message in the wireless network. The MSGin5Gserver includes an MSGin5G controller coupled with a processor and amemory. The MSGin5G controller is configured to receive the MSGin5Gmessage request from the source UE to deliver the message to the targetUE in the wireless network. Further, the MSGin5G controller isconfigured to determine whether the target UE supports the MSGin5Gtransport service using the TRF (based on MSGin5G service identity ofthe target UE) of the MSGin5G server upon receiving the MSGin5G messagerequest from the source UE. Further, the MSGin5G controller isconfigured to send the message to the target UE in response todetermining that the target UE supports the MSGin5G transport service.Further, the MSGin5G controller is configured to select the non-MSGin5Ggateway in the wireless network using the GWSF of the MSGin5G server inresponse to determining that the target UE does not support the MSGin5Gtransport service. Further, the MSGin5G controller is configured to sendthe message to the non-MSGin5G gateway.

Accordingly, embodiments herein disclose the non-MSGin5G gateway fordelivering the MSGin5G message in the wireless network. The non-MSGin5Ggateway includes an MSGin5G controller coupled with a processor and amemory. The MSGin5G controller is configured to translate the MSGin5Gmessage request according to the non-MSGin5G transport service using theTF of the non-MSGin5G gateway and the non-MSGin5G gateway sends themessage to the target UE after translation.

These and other aspects of the embodiments herein will be betterappreciated and understood when considered in conjunction with thefollowing description and the accompanying drawings. It should beunderstood, however, that the following descriptions, while indicatingpreferred embodiments and numerous specific details thereof, are givenby way of illustration and not of limitation. Many changes andmodifications may be made within the scope of the embodiments hereinwithout departing from the spirit thereof, and the embodiments hereininclude all such modifications.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated in the accompanying drawings,throughout which like reference letters indicate corresponding parts inthe various figures. The embodiments herein will be better understoodfrom the following description with reference to the drawings, in which:

FIG. 1 illustrates an architecture of an MSGin5G application service asspecified in 3GPP TS 23.554 v0.3.0, according to the embodiments asdisclosed herein;

FIG. 2A illustrates a block diagram of an MSGin5G server for deliveringan MSGin5G message in a wireless network, according to an embodiment asdisclosed herein;

FIG. 2B illustrates a block diagram of a non-MSGin5G gateway fordelivering the MSGin5G message in the wireless network, according to anembodiment as disclosed herein;

FIG. 3 is a flow diagram illustrating a method for delivering theMSGin5G message in the wireless network, according to an embodiment asdisclosed herein;

FIG. 4 is a sequence diagram illustrating various operations for sendingthe MSGin5G message from a source UE to a target UE in the wirelessnetwork where both the source UE and the target UE support an MSGin5Gtransport service, according to an embodiment as disclosed herein;

FIG. 5 is a sequence diagram illustrating various operations for sendingthe MSGin5G message from the source UE to the target UE in the wirelessnetwork where the source UE supports the MSGin5G transport service andthe target UE acts as legacy 3GPP UE that supports a non-MSGin5Gtransport service, according to an embodiment as disclosed herein; and

FIG. 6 is a sequence diagram illustrating various operations for sendingthe MSGin5G message from the source UE to the target UE in the wirelessnetwork where the source UE supports the MSGin5G transport service andthe target UE acts as non-3GPP UE that supports the non-MSGin5Gtransport service, according to an embodiment as disclosed herein.

DETAILED DESCRIPTION

FIGS. 1 through 6, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

The embodiments herein and the various features and advantageous detailsthereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings anddetailed in the following description. Descriptions of well-knowncomponents and processing techniques are omitted so as to notunnecessarily obscure the embodiments herein. Also, the variousembodiments described herein are not necessarily mutually exclusive, assome embodiments can be combined with one or more other embodiments toform new embodiments. The term “or” as used herein, refers to anon-exclusive or, unless otherwise indicated. The examples used hereinare intended merely to facilitate an understanding of ways in which theembodiments herein can be practiced and to further enable those skilledin the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

As is traditional in the field, embodiments may be described andillustrated in terms of blocks which carry out a described function orfunctions. These blocks, which may be referred to herein as managers,units, modules, hardware components or the like, are physicallyimplemented by analog and/or digital circuits such as logic gates,integrated circuits, microprocessors, microcontrollers, memory circuits,passive electronic components, active electronic components, opticalcomponents, hardwired circuits and the like, and may optionally bedriven by firmware. The circuits may, for example, be embodied in one ormore semiconductor chips, or on substrate supports such as printedcircuit boards and the like. The circuits constituting a block may beimplemented by dedicated hardware, or by a processor (e.g., one or moreprogrammed microprocessors and associated circuitry), or by acombination of dedicated hardware to perform some functions of the blockand a processor to perform other functions of the block. Each block ofthe embodiments may be physically separated into two or more interactingand discrete blocks without departing from the scope of the disclosure.Likewise, the blocks of the embodiments may be physically combined intomore complex blocks without departing from the scope of the disclosure.

Accordingly, embodiments herein disclose a method for delivering a 5thgeneration messages (MSGin5G) in a wireless network. The method includesreceiving, by an MSGin5G server, an MSGin5G message request from asource UE to deliver a message to a target UE in the wireless network.Further, the method includes determining, by the MSGin5G server, whetherthe target UE supports an MSGin5G transport service using a TRF (basedon MSGin5G service identity of the target UE) of the MSGin5G server uponreceiving the MSGin5G message request from the source UE. Further, themethod includes sending the message to the target UE in response todetermining that the target UE supports the MSGin5G transport service.Further, the method includes selecting a non-MSGin5G gateway in thewireless network using a GWSF of the MSGin5G server in response todetermining that the target UE does not support the MSGin5G transportservice. Further, the method includes sending the message to thenon-MSGin5G gateway, where the non-MSGin5G gateway translates theMSGin5G message request according to a non-MSGin5G transport serviceusing a TF of the non-MSGin5G gateway and the non-MSGin5G gateway sendsthe message to the target UE after translation.

Accordingly, embodiments herein disclose the MSGin5G server fordelivering the MSGin5G message in the wireless network. The MSGin5Gserver includes an MSGin5G controller coupled with a processor and amemory. The MSGin5G controller is configured to receive the MSGin5Gmessage request from the source UE to deliver the message to the targetUE in the wireless network. Further, the MSGin5G controller isconfigured to determine whether the target UE supports the MSGin5Gtransport service using the TRF (based on MSGin5G service identity ofthe target UE) of the MSGin5G server upon receiving the MSGin5G messagerequest from the source UE. Further, the MSGin5G controller isconfigured to send the message to the target UE in response todetermining that the target UE supports the MSGin5G transport service.Further, the MSGin5G controller is configured to select the non-MSGin5Ggateway in the wireless network using the GWSF of the MSGin5G server inresponse to determining that the target UE does not support the MSGin5Gtransport service. Further, the MSGin5G controller is configured to sendthe message to the non-MSGin5G gateway.

Accordingly, embodiments herein disclose the non-MSGin5G gateway fordelivering the MSGin5G message in the wireless network. The non-MSGin5Ggateway includes an MSGin5G controller coupled with a processor and amemory. The MSGin5G controller is configured to translate the MSGin5Gmessage request according to the non-MSGin5G transport service using theTF of the non-MSGin5G gateway and the non-MSGin5G gateway sends themessage to the target UE after translation.

Legacy 3GPP UE does not support MSGin5G and instead uses one of the3GPP-defined message delivery mechanisms (e.g., SMS, a NIDD), broadcast,etc.). Furthermore, a non-3GPP UE does not support the MSGin5G clientbut does support one of the non-3GPP message delivery mechanisms (e.g.,an RCS and a LwM2M, etc.).

The provided method in the present disclosure allows an MSGin5G serverto determine whether the target UE supports an MSGin5G transport serviceusing the TRF (based on MSGin5G service identity of the target UE) ofthe MSGin5G server upon receiving the MSGin5G message request from thesource UE to deliver the message (i.e., MSGin5G message) to the targetUE in the wireless network. Furthermore, the MSGin5G server sends themessage to the target UE in response to determining that the target UEsupports the MSGin5G transport service. Furthermore, the MSGin5G serverselects the non-MSGin5G gateway in the wireless network using the GWSFof the MSGin5G server in response to determining that the target UE doesnot support the MSGin5G transport service. Furthermore, the MSGin5Gserver sends the message to the non-MSGin5G gateway, where thenon-MSGin5G gateway translates the MSGin5G message request according tothe non-MSGin5G transport service using the TF of the non-MSGin5Ggateway and the non-MSGin5G gateway sends the message to the target UEafter translation. As a result, even if the target UE does not supportan MSGin5G message payload/MSGin5G client, the source UE (i.e., MSGin5GUE) sends the message to the target UE (e.g., MSGin5G UE, legacy 3GPPUE, non-3GPP UE, etc.) and the target UE does not require any externalhardware to communicate with the source UE.

The provided method in the present disclosure allows the MSGin5G serverto determine whether MSGin5G service identity of the target UE isregistered in a MSGin5G UE registration repository of the MSGin5Gserver. Furthermore, the MSGin5G server detects that the target UEsupports the MSGin5G transport service in response to determining thatthe target UE is registered in the MSGin5G UE registration repository ofthe MSGin5G server. Furthermore, the MSGin5G server detects that thetarget UE supports the non-MSGin5G transport service in response todetermining that the target UE is not registered in the MSGin5G UEregistration repository of the MSGin5G server.

The provided method in the present disclosure allows the MSGin5G serverto detect that the target UE is one of a legacy 3GPP UE and a non-3GPPUE based on a UE registration repository of an HSS and/or a UDM in thewireless network.

Referring now to the drawings and more particularly to FIGS. 1 through6, where similar reference characters denote corresponding featuresconsistently throughout the figures, there are shown preferredembodiments.

FIG. 1 illustrates an architecture of an MSGin5G application service(1000) as specified in 3GPP TS 23.554 according to the embodiments asdisclosed herein.

The MSGin5G application service (1000) includes an MSGin5G server (200),a SEAL server(s) (200A), an application server(s) (200B), a source UE(100A) (i.e., MSGin5G UE-1), a target UE (100B) (MSGin5G UE-2 (100Ba) ora legacy 3GPP UE (100Bb) or a non-3GPP UE (100Bc)), a non-MSGin5Ggateway (300) (a legacy 3GPP message gateway (300A) or a non-3GPPmessage gateway (300B)), a 3GPP core network(s) (400).

In an embodiment, the MSGin5G server (200) provides server-sidefunctionality to assist an MSGin5G clients (e.g., MSGin5G UE-1 (100A),MSGin5G UE-2 (100Ba) etc.) with sending and receiving of message(s) viaMSGin5G Service to/from the application server(s) (200B) and/or otherMSGin5G service endpoints on other UEs (e.g., the legacy 3GPP UE(100Bb), the non-3GPP UE (100Bc), etc.). To resolve a message deliverymechanism for the MSGin5G service endpoint based on a terminatingMSGSin5G service ID to determine, by the MSGin5G server (200), if themessage(s) is to be delivered to the target UE (100B), the applicationserver(s) (200B) or the non-MSGin5G gateway (300) for final delivery.

In an embodiment, the MSGin5G server (200) includes a TRF (241) and aGWSF (242), not shown in FIG. 1. The TRF (241) provides functionality toassist the MSGin5G server (200) to determine transport service(s)supported by the target UE (100B). Upon receiving an MSGin5G messagerequest, the TRF (241) checks a MSGin5G UE registration repository(database created at the time of each MSGin5G UE (e.g., MSGin5G UE-1(100A), MSGin5G UE-2 (100Ba), etc.) registration to the MSGin5G server(200)) of the MSGin5G server (200) for a target endpoint identifier(i.e., the target UE (100B)). If the target endpoint identifier is foundin the repository, then the transport service(s) supported by the targetUE (100B) is confirmed as the MSGin5G UE and can understand an MSGin5Gmessage payload. If the target endpoint identifier is not found in therepository, the MSGin5G server (200) checks a repository at HSS/UDM forthe target endpoint identifier. If the target endpoint identifier isfound in the repository of the HSS/UDM, then the transport service(s)supported by the target UE (100B) is determined as a non-MSGin5Gtransport service and need for support of the non-MSGin5G gateway (300)to understand the MSGin5G message payload.

Furthermore, the GWSF (242) provides functionality to assist the MSGin5Gserver (200) to determine the non-MSGin5G gateway (300) (the legacy 3GPPmessage gateway (300A) or the non-3GPP message gateway (300B)) suitableto the transport service(s) supported by the target UE (100B). Uponreceiving the transport service(s) determined by the TRF (241) andsupported by the target UE (100B), the GWSF (242) selects thecorresponding the non-MSGin5G gateway (300) (the legacy 3GPP messagegateway (300A) or the non-3GPP message gateway (300B)) based on amapping table available on the GWSF (242).

In an embodiment, the non-MSGin5G gateway (300) (the legacy 3GPP messagegateway (300A) and/or the non-3GPP message gateway (300B)) includes a TF(341), not shown in FIG. 1. The TF (341) performs conversion of theaddress of the target UE (100B) that is understood in a destinationdomain and conversion of protocols and payload according to thetransport service(s) supported by the target UE (100B).

In an embodiment, the non-MSGin5G gateway (300) in MSGin5G applicationarchitecture provides functionality to deliver MSGin5G messages tonon-MSGin5G UEs (i.e., the legacy 3GPP UE (100Bb) and the non-3GPP UE(100Bc)). The non-MSGin5G gateway (300) performs a role ofinterconnecting two different messaging delivery mechanisms and assuresmessage integrity between different message delivery mechanisms. Amessage delivery mechanism comprises a specific set of protocols,procedures, and rules.

In an embodiment, the non-MSGin5G gateway (300) enables seamlessdelivery of the MSGin5G message between different message deliverymechanisms with integrity. Furthermore, the non-MSGin5G gateway (300)communicates with the MSGin5G server (200) using either the MSGin5Gclient functionality or similar functions to enable sending andreceiving the MSGin5G messages. Furthermore, the non-MSGin5G gateway(300) delivers a payload of the MSGin5G message to the non-MSGin5G UE(i.e., the legacy 3GPP UE (100Bb) and the non-3GPP UE (100Bc)) using thespecific message delivery mechanism available to that non-MSGin5G UE andvice versa. Furthermore, the non-MSGin5G gateway (300) performs messagesender and receiver addresses conversion according to the two connectedmessage delivery mechanisms and maintain a mapping of the address pairused for a response message delivery. Furthermore, the non-MSGin5Ggateway (300) performs registration and de-registration with the MSGin5Gserver (200) on behalf of the non-MSGin5G UEs. Furthermore, thenon-MSGin5G gateway (300) acts as a service endpoint to perform messagesegmentation and reassembly for the non-MSGin5G UEs when needed.Furthermore, the non-MSGin5G gateway (300) performs protocol andnon-message payload information conversion according to the servicesupported by the target UE (100B).

In an embodiment, the legacy 3GPP message gateway (300A) is used todeliver the MSGin5G message to the Legacy 3GPP UEs (100Bb), using their3GPP supported message delivery mechanisms. Furthermore, the non-3GPPmessage gateway (300B) is used to deliver the MSGin5G message tonon-3GPP UEs (100Bc), using their (non-3GPP) supported message deliverymechanisms.

In an embodiment, the TRF (241) and the GWSF (242) are residing in theMSGin5G server (200) and the TF (341) resides in the message gateway. Inthis embodiment, each of logical functions (the TRF (241), the GWSF(242) and the TF (341)) performs their respective roles and thefunctionality over interface which is internal to MSGin5G server (200).

In an embodiment, all the logical functions (the TRF (241), the GWSF(242) and the TF (341)) can be co-located with another entity in theMSGin5G application service (1000) and in such cases; the relatedinterface functionality is internal to the entity hosting the logicalfunction.

FIG. 2A illustrates a block diagram of the MSGin5G server (200) fordelivering the MSGin5G message in the wireless network according to anembodiment as disclosed herein.

In an embodiment, the MSGin5G server (200) includes a memory (210), aprocessor (220), a communicator (230), and an MSGin5G controller (240).

The memory (110) stores the MSGin5G service identify (ID) of the sourceUE (100A), an MSGin5G service ID of the target UE (100B), and message IDinformation elements, the message ID information, a delivery status, anapplication ID, a payload, priority type information elements, andMSGin5G UE registration repository. Further, the memory (210) alsostores instructions to be executed by the processor (220). The memory(210) may include non-volatile storage elements. Examples of suchnon-volatile storage elements may include magnetic hard discs, opticaldiscs, floppy discs, flash memories, or forms of electricallyprogrammable memories (EPROM) or electrically erasable and programmable(EEPROM) memories. In addition, the memory (210) may, in some examples,be considered a non-transitory storage medium. The term “non-transitory”may indicate that the storage medium is not embodied in a carrier waveor a propagated signal. However, the term “non-transitory” should not beinterpreted that the memory (210) is non-movable. In some examples, thememory (210) can be configured to store larger amounts of information.In certain examples, a non-transitory storage medium may store data thatcan, over time, change (e.g., in random access memory (RAM) or cache).The memory (210) can be an internal storage unit or the memory can be anexternal storage unit of the MSGin5G server (200), a cloud storage, orany other type of external storage.

The processor (220) communicates with the memory (210), the communicator(230), and the MSGin5G controller (240). The processor (220) isconfigured to execute instructions stored in the memory (210) and toperform various processes. The processor (220) may include one or aplurality of processors, maybe a general-purpose processor, such as acentral processing unit (CPU), an application processor (AP), or thelike, a graphics-only processing unit such as a graphics processing unit(GPU), a visual processing unit (VPU), and/or an artificial intelligence(AI) dedicated processor such as a neural processing unit (NPU).

The communicator (230) includes an electronic circuit specific to astandard that enables wired or wireless communication. The communicator(230) is configured for communicating internally between internalhardware components and with external devices via one or more networks.

In an embodiment, the MSGin5G controller (240) is implemented byprocessing circuitry such as logic gates, integrated circuits,microprocessors, microcontrollers, memory circuits, passive electroniccomponents, active electronic components, optical components, hardwiredcircuits, or the like, and may optionally be driven by firmware. Thecircuits may, for example, be embodied in one or more semiconductors.

In an embodiment, the MSGin5G controller (240) includes the TRF (241)and the GWSF (242). The MSGin5G controller (240) is configured toreceive the MSGin5G message request from the source UE (100A) to deliverthe message to the target UE (100B) in the wireless network. Further,the MSGin5G controller (240) is configured to determine whether thetarget UE (100B) supports the MSGin5G transport service using the TRF(241) of the MSGin5G server (200) upon receiving the MSGin5G messagerequest from the source UE (100A). Further, the MSGin5G controller (240)is configured to send the message to the target UE (100B) in response todetermining that the target UE (100B) supports the MSGin5G transportservice. Further, the MSGin5G controller (240) is configured to selectthe non-MSGin5G gateway (300) in the wireless network using the GWSF(242) of the MSGin5G server (200) in response to determining that thetarget UE (100B) does not support the MSGin5G transport service.Further, the MSGin5G controller (240) is configured to send the messageto the non-MSGin5G gateway (300).

Further, the MSGin5G controller (240) is configured to determine whetherthe target UE (100B) is registered in the MSGin5G UE registrationrepository of the MSGin5G server (200). Further, the MSGin5G controller(240) is configured to detect that the target UE (100B) supports theMSGin5G transport service in response to determining that the target UE(100B) is registered in the MSGin5G UE registration repository of theMSGin5G server (200). Further, the MSGin5G controller (240) isconfigured to detect that the target UE (100B) supports the non-MSGin5Gtransport service in response to determining that the target UE (100B)is not registered in the MSGin5G UE registration repository of theMSGin5G server (200).

Further, the MSGin5G controller (240) is configured to detect that thetarget UE (100B) is registered in the UE registration repository of theHSS and/or the UDM in the wireless network. Further, the MSGin5Gcontroller (240) is configured to select one of the legacy 3GPP messagegateway (300A) and the non-3GPP message gateway (300B). Further, theMSGin5G controller (240) is configured to perform an authentication ofthe source UE (100A). Further, the MSGin5G controller (240) isconfigured to send the message to one of the legacy 3GPP message gateway(300A) and the non-3GPP message gateway (300B) based on selection.

Although the FIG. 2A shows various hardware components of the MSGin5Gserver (200) but it is to be understood that other embodiments are notlimited thereon. In other embodiments, the MSGin5G server (200) mayinclude less or more number of components. Further, the labels or namesof the components are used only for illustrative purpose and does notlimit the scope of the disclosure. One or more components can becombined together to perform same or substantially similar function todeliver the MSGin5G in the wireless network.

FIG. 2B illustrates a block diagram of the non-MSGin5G gateway (300) fordelivering the MSGin5G message in the wireless network, according to anembodiment as disclosed herein.

In an embodiment, the non-MSGin5G gateway (300) includes a memory (310),a processor (320), a communicator (330), and an MSGin5G controller(340).

The memory (310) stores the MSGin5G service identify (ID) of the sourceUE (100A), an MSGin5G service ID of the target UE (100B), and message IDinformation, a delivery status, an application ID, a payload, prioritytype information elements, and UE registration repository of the HSS andthe UDM. Further, the memory (310) also stores instructions to beexecuted by the processor (320). The memory (310) may includenon-volatile storage elements. Examples of such non-volatile storageelements may include magnetic hard discs, optical discs, floppy discs,flash memories, or forms of electrically programmable memories (EPROM)or electrically erasable and programmable (EEPROM) memories. Inaddition, the memory (310) may, in some examples, be considered anon-transitory storage medium. The term “non-transitory” may indicatethat the storage medium is not embodied in a carrier wave or apropagated signal. However, the term “non-transitory” should not beinterpreted that the memory (310) is non-movable. In some examples, thememory (310) can be configured to store larger amounts of information.In certain examples, a non-transitory storage medium may store data thatcan, over time, change (e.g., in Random Access Memory (RAM) or cache).The memory (310) can be an internal storage unit or the memory (310) canbe an external storage unit of the non-MSGin5G gateway (300), a cloudstorage, or any other type of external storage.

The processor (320) communicates with the memory (310), the communicator(330), and the MSGin5G controller (340). The processor (220) isconfigured to execute instructions stored in the memory (310) and toperform various processes. The processor (320) may include one or aplurality of processors, maybe a general-purpose processor, such as aCPU, an AP, or the like, a graphics-only processing unit such as a GPU,a VPU, and/or an AI dedicated processor such as an NPU.

The communicator (330) includes an electronic circuit specific to astandard that enables wired or wireless communication. The communicator(330) is configured for communicating internally between internalhardware components and with external devices via one or more networks.

In an embodiment, the MSGin5G controller (340) is implemented byprocessing circuitry such as logic gates, integrated circuits,microprocessors, microcontrollers, memory circuits, passive electroniccomponents, active electronic components, optical components, hardwiredcircuits, or the like, and may optionally be driven by firmware. Thecircuits may, for example, be embodied in one or more semiconductors.

In an embodiment, the MSGin5G controller (340) includes the TF (341).The MSGin5G controller (340) is configured to translate the MSGin5Gmessage request according to the non-MSGin5G transport service using theTF (341) of the non-MSGin5G gateway (300) and the non-MSGin5G gateway(300) sends the message to the target UE (100B) after translation.

Further, the MSGin5G controller (340) is configured to determine themessage delivery mechanism to send the message to the target UE (100B)based on the capability of the target UE (100B), the communicationstatus of the target UE (100B), and the service configuration of thetarget UE (100B), where the message delivery mechanism is one of the SMSand the NIDD. Further, the MSGin5G controller (340) is configured toperform the registration and the de-registration with the MSGin5G server(200) for the non-MSGin5G UE. Further, the MSGin5G controller (340) isconfigured to perform the segmentation of the message and reassemblingof the message for the non-MSGin5G UE. Further, the MSGin5G controller(340) is configured to perform conversion of an address of the target UE(100B). Further, the MSGin5G controller (340) is configured to translateprotocols, and non-message payload information of the message based onthe determined message delivery mechanism. Further, the MSGin5Gcontroller (340) is configured to send the message to the target UE(100B). Further, the MSGin5G controller (340) is configured to send theMSGin5G message delivery report to the MSGin5G server (200).

Further, the MSGin5G controller (340) is configured to determine themessage delivery mechanism to send the message to the target UE (100B)based on the capability of the target UE (100B), the communicationstatus of the target UE (100B), and the service configuration of thetarget UE (100B), where the message delivery mechanism is one of the RCSand the LwM2M. Further, the MSGin5G controller (340) is configured totranslate the message into the non-3GPP message based on the determinedmessage delivery mechanism. Further, the MSGin5G controller (340) isconfigured to send the message to the target UE (100B). Further, theMSGin5G controller (340) is configured to send the MSGin5G messagedelivery report to the MSGin5G server (200).

Although the FIG. 2B various hardware components of the non-MSGin5Ggateway (300) but it is to be understood that other embodiments are notlimited thereon. In other embodiments, the non-MSGin5G gateway (300) mayinclude less or more number of components. Further, the labels or namesof the components are used only for illustrative purpose and does notlimit the scope of the disclosure. One or more components can becombined together to perform same or substantially similar function todeliver the MSGin5G in the wireless network.

FIG. 3 is a flow diagram (S300) illustrating a method for delivering theMSGin5G message in the wireless network, according to an embodiment asdisclosed herein. The operations (S302-S312) are performed by theMSGin5G server (200) and the non-MSGin5G gateway (300).

At S302, the method includes receiving the MSGin5G message request fromthe source UE (100A) to deliver the message to the target UE (100B) inthe wireless network. At S304, the method includes determining whetherthe target UE (100B) supports the MSGin5G transport service using theTRF (based on MSGin5G service identity of the target UE) of the MSGin5Gserver (200). At S306, the method includes determining action (e.g.,S308, S310) based on whether the target UE (100B) supports the MSGin5Gtransport service using a TRF (241) of the MSGin5G server (200) uponreceiving the MSGin5G message request from the source UE (100A). AtS308, the method includes sending the message to the target UE (100B) inresponse to determining that the target UE (100B) supports the MSGin5Gtransport service.

At S310, the method includes selecting the non-MSGin5G gateway (300) inthe wireless network using the GWSF (242) of the MSGin5G server (200) inresponse to determining that the target UE (100B) does not support theMSGin5G transport service. At S312, the method includes sending themessage to the non-MSGin5G gateway (300), where the non-MSGin5G gateway(300) translates the MSGin5G message request according to thenon-MSGin5G transport service using the TF (341) of the non-MSGin5Ggateway (300) and the non-MSGin5G gateway (300) sends the message to thetarget UE (100B) after translation.

The various actions, acts, blocks, steps, or the like in the flowdiagram (S300) may be performed in the order presented, in a differentorder or simultaneously. Further, in some embodiments, some of theactions, acts, blocks, steps, or the like may be omitted, added,modified, skipped, or the like without departing from the scope of thedisclosure.

FIG. 4 is a sequence diagram illustrating various operations for sendingthe MSGin5G message from the source UE (100A) to the target UE (100B) inthe wireless network where both the source UE (100A) and the target UE(100B) support the MSGin5G transport service, according to an embodimentas disclosed herein.

For this scenario, pre-condition is MSGin5G client-2 of the MSGin5G UE-2(100Ba)/target UE (100B) is registered to the MSGin5G server (200). At401, the MSGin5G server (200) has received a valid MSGin5G message fromthe source UE (100A) (i.e., MSGin5G UE-1). At 402, the TRF (241) checksthe registry repository of the MSGin5G server (200) to find the targetendpoint identifier as specified in the received MSGin5G message. TheTRF (241) finds the registry information about the target endpointidentifier and resolves to send the MSGin5G message to the MSGin5G UE-2(100Ba) identified by the target endpoint identifier. At 403, theMSGin5G server (200) forwards the MSGin5G message request to the MSGin5GUE-2 (100Ba) (i.e., MSGin5G clien-2 (100Baa)/ application client(100Bab)). At 404, the MSGin5G UE-2 (100Ba) delivers contents of theMSGin5G message to the targeted application client/the MSGin5G UE-2(100Ba)/ target UE (100B).

FIG. 5 is a sequence diagram illustrating various operations for sendingthe MSGin5G message from the source UE (100A) to the target UE (100B) inthe wireless network where the source UE (100A) supports the MSGin5Gtransport service and the target UE (100B) acts as the legacy 3GPP UE(100Bb) that supports the non-MSGin5G transport service, according to anembodiment as disclosed herein.

As per 3GPP TS 23.554, for this scenario, pre-conditions are givenbelow:

-   -   i. MSGin5G Client in MSGin5G UE (source UE (100A)) is registered        with the MSGin5G server (200);    -   ii. The legacy 3GPP message gateway (300A) is aware of the        MSGin5G service ID of the legacy 3GPP UE (100Bb) and maintains        the mapping to IDs used in a legacy network; and/or    -   iii. The MSGin5G server (200) can determine whether the target        UE (100B) is the legacy 3GPP UE (100Bb), and which message        delivery mechanisms are available.

At 501, the source UE (100A) sends the MSGin5G message request to theMSGin5G server (200). The MSGin5G message request includes an MSGin5Gservice identify (ID) of the source UE (100A), an MSGin5G service ID ofthe target UE (100B), message ID information a delivery status, anapplication ID, a payload, and priority type information elements. At502, upon receiving the MSGin5G message request, the MSGin5G server(200) determines that the recipient is the legacy 3GPP UE (100Bb) andthe MSGin5G client (source UE (100A)) is authorized to send the MSGin5Gmessage to the legacy 3GPP UE (100Bb). At 503, the MSGin5G server (200)forwards the MSGin5G message request to the legacy 3GPP message gateway(300A).

At 504, the legacy 3GPP message gateway (300A) determines which legacy3GPP message delivery mechanism (e.g., SMS, NIDD, etc.) uses based on acapability of the target UE (100B)/legacy 3GPP UE (100Bb), acommunication status of the target UE (100B)/legacy 3GPP UE (100Bb), anda service configuration of the target UE (100B)/legacy 3GPP UE (100Bb),etc. When selected, the legacy 3GPP message gateway (300A) maps theMSGin5G service ID to the corresponding identifier. For example (not anexhaustive list), as given below:

-   -   i. If the legacy 3GPP message gateway (300A) selected the device        triggering, the legacy 3GPP message gateway (300A) maps the        service ID to MSISDN and Application port ID;    -   ii. If the legacy 3GPP message gateway (300A) selected the NIDD        delivery mechanism, the legacy 3GPP message gateway (300A) maps        the service ID to External Identifier or MSISDN; and/or    -   iii. If the legacy 3GPP message gateway (300A) selected the SMS        delivery mechanism, the legacy 3GPP message gateway (300A) maps        the service ID to MSISDN.

At 505-513, the legacy 3GPP message gateway (300A) sends the payload ofthe MSGin5G message to the legacy 3GPP UE (100Bb). For example (not anexhaustive list), as given below:

-   -   i. For the device triggering (505), the legacy 3GPP message        gateway (300A) maps the payload of the MSGin5G message to one or        more device triggering requests (see 3GPP TS 23.682, 3GPP TS        29.122, and 3GPP TS 29.522);    -   ii. For the NIDD delivery mechanism (506), the legacy 3GPP        message gateway (300A) maps the payload of the MSGin5G message        to one or more NIDD submit request messages (see 3GPP TS 23.682,        3GPP TS 29.122, and 3GPP TS 29.522). Alternatively, if tunnel        parameters are provisioned in the legacy 3GPP message gateway        (see 3GPP TS 23.401, 3GPP TS 23.501, and 3GPP TS 23.502); and/or    -   iii. For the SMS delivery mechanism (507), the legacy 3GPP        message gateway (300A) sends SMS to the legacy 3GPP UE (100Bb)        according to the procedure in 3GPP TS 23.204 or the procedure in        3GPP TS 23.502.

At 508-509, If delivery status required is included in the MSGin5Gmessage request, the legacy 3GPP message gateway (300A) sends MSGin5Gmessage delivery report to the MSGin5G server (200), the MSGin5G server(200) sends the delivery report to the MSGin5G client (source UE (100A))as specified in 3GPP TS 23.554.

FIG. 6 is a sequence diagram illustrating various operations for sendingthe MSGin5G message from the source UE (100A) to the target UE (100B) inthe wireless network where the source UE (100A) supports the MSGin5Gtransport service and the target UE (100B) acts as the non-3GPP UE(100Bc) that supports the non-MSGin5G transport service, according to anembodiment as disclosed herein.

As per 3GPP TS 23.554, for this scenario, pre-conditions are givenbelow:

-   -   i. MSGin5G Client in MSGin5G UE (source UE (100A)) is registered        with the MSGin5G server (200); and/or    -   ii. The on-3GPP message gateway (300B) is aware of the non-3GPP        message client in non-3GPP UE (100Bc) and provides the mapping        to MSGin5G service ID.

At 601, the source UE (100A) sends the MSGin5G message request to theMSGin5G server (200). The MSGin5G message request includes an MSGin5Gservice identify (ID) of the source UE (100A), an MSGin5G service ID ofthe target UE (100B), and message ID information, a delivery status, anapplication ID, a payload, and priority type information elements. At602, the MSGin5G server (200) determines the recipient is the non-3GPPUE (100Bc) and the MSGin5G Client is authorized to send the MSGin5Gmessage to the non-3GPP UE (100Bc).

At 603, the MSGin5G server (200) forwards the MSGin5G message request tothe non-3GPP message gateway (300B) as specified in 3GPP TS 23.554. At604, the non-3GPP message gateway (300B) translates the MSGin5G messageto the non-3GPP message with the delivery report requested and sends thenon-3GPP message to the non-3GPP Message client (the target UE (100B)).At 605, If a delivery status report is required, the non-3GPP messagegateway (300B)sends the MSGin5G message delivery report to the MSGin5Gserver (200), the MSGin5G server (200) forwards the MSGin5G messagedelivery report to the MSGin5G client (source UE (100A)).

In one embodiment, massive Internet of Things (MIoT) is one of keysegment(s) of the 5G system. message service including legacy 3GPP andnon-3GPP UEs widens the scope of the MSgin5G Service through theapplicability of the provided method.

The embodiments disclosed herein can be implemented using at least onehardware device and performing network management functions to controlthe elements.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, byapplying current knowledge, readily modify and/or adapt for variousapplications such specific embodiments without departing from thegeneric concept, and, therefore, such adaptations and modificationsshould and are intended to be comprehended within the meaning and rangeof equivalents of the disclosed embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose ofdescription and not of limitation. Therefore, while the embodimentsherein have been described in terms of preferred embodiments, thoseskilled in the art will recognize that the embodiments herein can bepracticed with modification within the scope of the embodiments asdescribed herein.

Although the present disclosure has been described with variousembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method for delivering a 5^(th) generationmessage) (MSGin5G) in a wireless network, the method comprising:receiving, by an MSGin5G server, an MSGin5G message request from asource user equipment (UE) (100A) to deliver a message to a target UE inthe wireless network, determining, by the MSGin5G server, whether thetarget UE supports an MSGin5G transport service using a targetresolution function (TRF) of the MSGin5G server upon receiving theMSGin5G message request from the source UE; and sending, by the MSGin5Gserver, the message to the target UE in response to determining that thetarget UE supports the MSGin5G transport service.
 2. The method asclaimed in claim 1, further comprising: selecting, by the MSGin5Gserver, a non-MSGin5G gateway in the wireless network using a gatewayselection function (GWSF) of the MSGin5G server in response todetermining that the target UE does not support the MSGin5G transportservice; and sending, by the MSGin5G server, the message to thenon-MSGin5G gateway, wherein the non-MSGin5G gateway translates theMSGin5G message request according to a non-MSGin5G transport serviceusing a translation function (TF) of the non-MSGin5G gateway and thenon-MSGin5G gateway sends the message to the target UE aftertranslation.
 3. The method as claimed in claim 1, wherein the MSGin5Gmessage request comprises at least one of an MSGin5G service identity(ID) of the source UE, an MSGin5G service ID of the target UE, messageID information, a delivery status, an application ID, a payload, orpriority type information elements.
 4. The method as claimed in claim 1,wherein a non-MSGin5G transport service comprises at least one of alegacy 3rd generation partnership project (3GPP) transport service or anon-3GPP transport service.
 5. The method as claimed in claim 1, whereina non-MSGin5G gateway comprises at least one of a legacy 3GPP messagegateway or a non-3GPP message gateway.
 6. The method as claimed in claim5, wherein the legacy 3GPP message gateway is used to deliver themessage to the target UE using a 3GPP transport service and the non-3GPPmessage gateway is used to deliver the message to the target UE using anon-3GPP transport service.
 7. The method as claimed in claim 1, whereinthe source UE is an MSGin5G UE and the target UE is one of the MSGin5GUE or a non-MSGin5G UE, and wherein the MSGin5G UE supports the MSGin5Gtransport service and the target UE supports at least one of the MSGin5Gtransport service or a non-MSGin5G transport service.
 8. The method asclaimed in claim 7, wherein the non-MSGin5G UE is one of a legacy 3GPPUE or a non-3GPP UE.
 9. The method as claimed in claim 1, whereindetermining, by the MSGin5G server , whether the target UE supports theMSGin5G transport service using the TRF of the MSGin5G server uponreceiving the MSGin5G message request from the source UE comprises:determining, by the MSGin5G server, whether the target UE is registeredin a MSGin5G UE registration repository of the MSGin5G server;performing, by the MSGin5G server (200), one of: detecting that thetarget UE supports the MSGin5G transport service in response todetermining that the target UE is registered in the MSGin5G UEregistration repository of the MSGin5G server; or detecting that thetarget UE supports a non-MSGin5G transport service in response todetermining that the target UE is not registered in the MSGin5G UEregistration repository of the MSGin5G server.
 10. The method as claimedin claim 9, wherein detecting that the target UE supports a legacy 3GPPtransport service comprises: detecting, by the MSGin5G server, that thetarget UE is registered in a UE registration repository of at least oneof a home subscriber server (HSS) and a unified data management (UDM) inthe wireless network.
 11. The method as claimed in claim 9, whereindetecting that the target UE supports a non-3GPP transport servicecomprises: detecting, by the MSGin5G server, that the target UE is notregistered in the MSGin5G UE registration repository and is notregistered in a registration repository of at least one of a HSS or aUDM in the wireless network.
 12. The method as claimed in claim 1,wherein selecting a non-MSGin5G gateway in the wireless network using aGWSF of the MSGin5G server comprises: selecting, by the MSGin5G server(200), one of a legacy 3GPP message gateway or a non-3GPP messagegateway based on a mapping table available at the GWSF ; performing, bythe MSGin5G server, an authentication procedure of the source UE ; andsending, by the MSGin5G server (200), the message to one of the legacy3GPP message gateway or the non-3GPP message gateway based on a resultof a selection.
 13. The method as claimed in claim 1, whereintranslating the MSGin5G message request according to a non-MSGin5Gtransport service using a TF comprises: detecting, by the MSGin5Gserver, that a legacy 3GPP message gateway is selected; determining, bythe legacy 3GPP message gateway, a message delivery mechanism to sendthe message to the target UE based on at least one of a capability ofthe target UE, a communication status of the target UE, or a serviceconfiguration of the target UE, wherein the message delivery mechanismis at least one of a short message service (SMS), a non-IP data delivery(NIDD), or a device triggering; performing, by the legacy 3GPP messagegateway, a registration and a de-registration with the MSGin5G serverfor a non-MSGin5G UE; performing, by the legacy 3GPP message gateway , asegmentation of the message and reassembling of the message for thenon-MSGin5G UE; performing, by the legacy 3GPP message gateway,conversion of an address of the target UE; translating, by the legacy3GPP message gateway, protocols, and non-message payload information ofthe message based on the determined message delivery mechanism; andsending, by the legacy 3GPP message gateway, the message to the targetUE.
 14. The method as claimed in claim 13, wherein the legacy 3GPPmessage gateway receives a delivery report from the target UE,translates the received delivery report into a MSGin5G message deliveryreport, and sends an MSGin5G message delivery report to the MSGin5Gserver.
 15. The method as claimed in claim 1, wherein translating theMSGin5G message request according to a non-MSGin5G transport serviceusing a TF comprises: detecting, by the MSGin5G server, that a non-3GPPmessage gateway is selected; determining, by the non-3GPP messagegateway, a message delivery mechanism to send the message to the targetUE based on a capability of the target UE, a communication status of thetarget UE, and a service configuration of the target UE, wherein themessage delivery mechanism is at least one of a rich communicationservices (RCS) or a lightweightM2M (LwM2M); translating, by the non-3GPPmessage gateway, the message into a non-3GPP message based on thedetermined message delivery mechanism; and sending, by the non-3GPPmessage gateway, the message to the target UE.
 16. The method as claimedin claim 15, wherein the non-3GPP message gateway receives a deliveryreport from the target UE, translates the received delivery report intoa MSGin5G message delivery report, and sends an MSGin5G message deliveryreport to the MSGin5G server.
 17. An MSGin5G server for delivering a5^(th) generation messages (MSGin5G) in a wireless network, the MSGin5Gserver comprising: memory; a processor; and a MSGin5G controller,operably connected to the memory and the processor (220), configured to:receive an MSGin5G message request from a source user equipment (UE) todeliver a message to a target UE in the wireless network, determinewhether the target UE supports an MSGin5G transport service using atarget resolution function (TRF) of the MSGin5G server upon receivingthe MSGin5G message request from the source UE; and send the message tothe target UE in response to determining that the target UE supports theMSGin5G transport service.
 18. The MSGin5G server as claimed in claim17, wherein the MSGin5G controller is further configured to: select anon-MSGin5G gateway in the wireless network using a gateway selectionfunction (GWSF) of the MSGin5G server in response to determining thatthe target UE does not support the MSGin5G transport service, and sendthe message to the non-MSGin5G gateway, wherein the non-MSGin5G gatewaytranslates the MSGin5G message request according to a non-MSGin5Gtransport service using a translation function (TF) of the non-MSGin5Ggateway and the non-MSGin5G gateway sends the message to the target UEafter translation.
 19. The MSGin5G server (200) as claimed in claim 17,wherein the MSGin5G message request comprises at least one of an MSGin5Gservice identity (ID) of the source UE, an MSGin5G service ID of thetarget UE, message ID information, a delivery status, an application ID,a payload, or priority type information elements.
 20. The MSGin5G serveras claimed in claim 17, wherein a non-MSGin5G transport servicecomprises at least one of a legacy 3^(rd) generation partnership project(3GPP) transport service or a non-3GPP transport service.